home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
SGI Cosmo Software 1997 May
/
SGI Cosmo Software 1997 May.iso
/
dist6.2
/
patchSG0001932.idb
/
usr
/
relnotes
/
patchSG0001932
/
ch1.z
/
ch1
Wrap
Text File
|
1997-05-23
|
9KB
|
265 lines
- 1 -
1. _P_a_t_c_h__S_G_0_0_0_1_9_3_2__R_e_l_e_a_s_e__N_o_t_e
This release note describes patch SG0001932 to IRIX6.2, 6.3
and 6.4.
Patch SG0001932 replaces patches(es) SG0001681, SG0001584,
SG0001384, SG0001336, and SG0001266.
1.1 _S_u_p_p_o_r_t_e_d__H_a_r_d_w_a_r_e__P_l_a_t_f_o_r_m_s
This patch contains bug fixes for all hardware platforms
running IRIX6.2, IRIX6.3, or IRIX6.4.
1.2 _S_u_p_p_o_r_t_e_d__S_o_f_t_w_a_r_e__P_l_a_t_f_o_r_m_s
This patch contains bug fixes to rld and rld.debug (all 3
ABIs) on a system running IRIX6.2, IRIX6.3, or IRIX6.4. The
software cannot be installed on other configurations.
1.3 _B_u_g_s__F_i_x_e_d__b_y__P_a_t_c_h__S_G_0_0_0_1_9_3_2
This patch allows programs using pthreads (POSIX threads) to
run correctly (a sufficiently recent pthreads version must
be run to see any improvement in application behavior).
This patch contains fixes for the following bugs in IRIX6.3,
6.3, 6.4: Bug numbers from a Silicon Graphics bug tracking
system are included for reference.
+o rld could hang a pthreads process if one or more
threads called fork(2) or if there were multiple
threads on a single sproc process-id or if a thread
moved from one process-id to another (in an sproc
group). Whether a hang occurred depended on the timing
of events and how the events happened to relate to rld
processing. In addition, an annoying message about
"GUARANTEE INIT" could be emitted by rld when the
message was inappropriate (with certain
processes/libraries using pthreads). (Bug #412725)
The following bug fixes were originally fixed in one or more
of the patches replaced by this patch.
+o rld could coredump if it thought it had allocated an
internal table (the msym table) but in reality the
compilation system had built it: writing to the
compiler-system-built table is an error (it is in
read-only memory) and unnecessary. (Bug #449282)
- 2 -
+o 433288 If a program did a series of dlclose(3)s and
sproc(2)s quickly enough and the timing was just right
rld would hang, hanging the program. The program was
killable, but the sproc-thread could not be continued
and the program run was normally useless as a result of
the hang. (But #433288)
+o The runtime linker corrupts the user's data segment
when long LD_LIBRARY_PATH is specified. It usually
results in segmentation fault while running the user
application. (Bug #337982)
+o The runtime linker does not fix-up binaries with
prefetch instructions correctly when the binaries are
run on r8000 machines. This fix is only effective if
one of the kernel rollup patches in the series
beginning with patch 1722 is also installed (as of the
writing of these release notes the latest kernel rollup
patch is patch 1733, but be sure to check with with
your patch provider about kernel rollup patches). The
runtime linker may emit a message like "Cannot open
<executable> to fix up prefetches" on attempting to run
a binary with prefetches (such as a binary compiled for
the R10000) on an R8000 CPU if one of the kernel
patches is not installed. (Bug #352206)
+o The runtime linker would core dump on pixified binaries
if those binaries contain prefetch instructions. (Bug
#383655)
+o The runtime linker loops when 2 delay-loaded libraries
are linked into the same executable and the 2 libraries
are inter-dependent on each other. Also, the
performance of the libdl routines are not acceptable in
big applications when hundreds of libraries are loaded
using dlopen calls. (Bug #361758)
+o Specifing LD_LIBRARY_PATH with more than approximately
500 characters causes rld to dump core. (Bug #337982)
+o The runtime linker loops in dlsym call. (Bug #364118)
+o The runtime linker loops when dlopen'ing libraries that
have inter-dependencies. (Bug #290198)
+o Initialized COMMON block variables have incorrect
values. (Bug #387407)
+o Dlopen(...,RTLD_NOW) does not report undefined symbols.
(Bug #428927)
- 3 -
1.4 _S_u_b_s_y_s_t_e_m_s__I_n_c_l_u_d_e_d__i_n__P_a_t_c_h__S_G_0_0_0_1_9_3_2
This patch release includes these subsystems:
+o patchSG0001932.compiler_eoe_sw.unix
+o patchSG0001932.compiler_eoe_sw32.unix
+o patchSG0001932.compiler_eoe_sw64.unix
1.5 _I_n_s_t_a_l_l_a_t_i_o_n__I_n_s_t_r_u_c_t_i_o_n_s
Because you want to install only the patches for problems
you have encountered, patch software is not installed by
default. After reading the descriptions of the bugs fixed
in this patch (see Section 1.3), determine the patches that
meet your specific needs.
If, after reading Sections 1.1 and 1.2 of these release
notes, you are unsure whether your hardware and software
meet the requirements for installing a particular patch, run
_i_n_s_t. The _i_n_s_t program does not allow you to install
patches that are incompatible with your hardware or
software.
Patch software is installed like any other Silicon Graphics
software product. Follow the instructions in your _S_o_f_t_w_a_r_e
_I_n_s_t_a_l_l_a_t_i_o_n _A_d_m_i_n_i_s_t_r_a_t_o_r'_s _G_u_i_d_e to bring up the miniroot
form of the software installation tools.
Follow these steps to select a patch for installation:
1. At the Inst> prompt, type
iiiinnnnssssttttaaaallllllll ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
where _x_x_x_x_x_x_x is the patch number.
2. Initiate the installation sequence. Type
IIIInnnnsssstttt>>>> ggggoooo
3. You may find that two patches have been marked as
incompatible. (The installation tools reject an
installation request if an incompatibility is
detected.) If this occurs, you must deselect one of
the patches.
IIIInnnnsssstttt>>>> kkkkeeeeeeeepppp ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
- 4 -
where _x_x_x_x_x_x_x is the patch number.
4. After completing the installation process, exit the
_i_n_s_t program by typing
IIIInnnnsssstttt>>>> qqqquuuuiiiitttt
1.6 _P_a_t_c_h__R_e_m_o_v_a_l__I_n_s_t_r_u_c_t_i_o_n_s
To remove a patch, use the _v_e_r_s_i_o_n_s _r_e_m_o_v_e command as you
would for any other software subsystem. The removal process
reinstates the original version of software unless you have
specifically removed the patch history from your system.
vvvveeeerrrrssssiiiioooonnnnssss rrrreeeemmmmoooovvvveeee ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
where _x_x_x_x_x_x_x is the patch number.
To keep a patch but increase your disk space, use the
_v_e_r_s_i_o_n_s _r_e_m_o_v_e_h_i_s_t command to remove the patch history.
vvvveeeerrrrssssiiiioooonnnnssss rrrreeeemmmmoooovvvveeeehhhhiiiisssstttt ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
where _x_x_x_x_x_x_x is the patch number.
1.7 _K_n_o_w_n__P_r_o_b_l_e_m_s